Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1532

reference: 116-tree-1
name: 1532
tree-preservation-order: undefined
116-tpo-1
uprn
address-text
point: POINT (-0.940520 50.865589)
geometry: MULTIPOLYGON (((-0.940464 50.865582,-0.940466 50.865594,-0.940474 50.865604,-0.940486 50.865612,-0.940502 50.865617,-0.940520 50.865619,-0.940537 50.865617,-0.940553 50.865612,-0.940566 50.865605,-0.940574 50.865595,-0.940577 50.865583,-0.940575 50.865572,-0.940567 50.865562,-0.940554 50.865554,-0.940539 50.865549,-0.940521 50.865547,-0.940504 50.865549,-0.940488 50.865554,-0.940475 50.865561,-0.940467 50.865571,-0.940464 50.865582)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL